Coder Social home page Coder Social logo

Comments (5)

lrhn avatar lrhn commented on July 3, 2024

since we're checking it based on the name.

Yeah, there's the issue.

Can you even do:

const myResource = ResourceIdentifier(...);

@myResource
Some declaration...

?

from sdk.

mosuem avatar mosuem commented on July 3, 2024

Yes, the current check is name and library only. I like the idea of subclassing!

from sdk.

dcharkes avatar dcharkes commented on July 3, 2024

I think we should likely disallow implementing, because the metadata field could not exist in a subclass.

Also, we should specify what happens to subclasses specifying more fields. Are they reported in the resources.json? If they are reported, we should come up with an encoding that does not lead to potential conflicts.

class JClassIdentifier extends ResourceIdentifier {
  final String name;

  const JClassIdentifier(this.name)
      : super('jnigen');
}

This would currently lead to a class between name in the annotation and name of the method the annotation is on in how it's currently encoded.

@mosuem @HosseinYousefi @lrhn Any preferences on if the metadata field is special and the only one reported, or if we report all fields?

from sdk.

HosseinYousefi avatar HosseinYousefi commented on July 3, 2024

@lrhn
Unrelated question: why can we create a const string but not a const map from const constructor's arguments?

class JClassIdentifier extends ResourceIdentifier {
  const JClassIdentifier(String name, String somethingElse)
      : super(const {name: somethingElse}); // Error!
}

I assume it's because the const string and string have the same syntax but const map requires an extra const keyword. It would be nice to have something like "preferConst" so we could do

class JClassIdentifier extends ResourceIdentifier {
  const JClassIdentifier(String name, String somethingElse)
      : super(preferConst {name: somethingElse}); 
}

Since making {name: somethingElse} to be "preferConst" by default is a breaking change.

from sdk.

HosseinYousefi avatar HosseinYousefi commented on July 3, 2024

Any preferences on if the metadata field is special and the only one reported, or if we report all fields?

Since we can't quite fill the metadata as a map using the arguments of the subclass' const constructor, I prefer it if we report all fields if possible.

from sdk.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.