Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Moose (Fame?) specific pragmas should have a Moose (Fame?) prefix #2308

Open
NicolasAnquetil opened this issue Jun 14, 2020 · 0 comments
Open

Moose (Fame?) specific pragmas should have a Moose (Fame?) prefix #2308

NicolasAnquetil opened this issue Jun 14, 2020 · 0 comments
Labels
enhancement Infrastructure

Comments

@NicolasAnquetil
Copy link
Contributor

Like <FMComment: >, <FMClass:super: >, <FMProperty:type: >, and <FMProperty:type:opposite: >

This would make it easier to search for them and be sure it does not collide with other pragmas from other packages

  • <container> could be <FMContainer> (this one looks like it could be used in other packages for other means)
  • <source> / <target> could be <FMSource> / <FMTarget>
  • <derived> could be <FMDerived>
  • <multivalued>
  • <navigation: ...>
  • <package:>
  • <abstract> (in #annotation methods, not sure whether this is for Pharo or Moose)
  • <mooseGroup> (related to Moose but not Famix, should we have two prefixes or put Moose everywhere even for Fame ?)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NicolasAnquetil