/osate2

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.

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

Verify method registry uses identifier to refer to Resolute function rather than qualified name #1301

Closed
reteprelief opened this Issue Jun 7, 2018 · 0 comments

Comments

Assignees

@reteprelief reteprelief

Labels
Projects
None yet
Milestone
  2.3.4
1 participant
@reteprelief
@reteprelief
Contributor

reteprelief commented Jun 7, 2018

The method registry could use a qualified name, which would get resolved by the global scope provided used by Verify.
The change can be made backward compatible.
Once all method registries use qualified references, we can remove the VierfyLinkingService.

@reteprelief reteprelief added this to the 2.3.4 milestone Jun 7, 2018

@reteprelief reteprelief self-assigned this Jun 7, 2018

@reteprelief reteprelief added alisa category:enhancement next labels Jun 7, 2018

@reteprelief reteprelief referenced this issue Jun 8, 2018

Merged

#1301 Use qualified Resolute claim or compute function name in verify method registry #1304

@wafflebot wafflebot bot added review and removed next labels Jun 8, 2018

@lwrage lwrage closed this in #1304 Jun 12, 2018

lwrage added a commit that referenced this issue Jun 12, 2018

@lwrage
Merge pull request #1304 from osate/Resolute_Invocation_Registry 
#1301 Use qualified Resolute claim or compute function name in verify method registry
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
1ce98ad

@wafflebot wafflebot bot removed the review label Jun 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment