You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, this feature #1539 relies on sequence names to determine how those sequences will be invoked via onboard command. In reality, the ID with which a sequence can be invoked will vary across FSWs. We need a multi-FSW way to determine what the correct invocable id is for any given sequence. Examples: for FCPL seqs, the invocable ID is the onboard name, but for VML, the invocable Id is the seqid.
Describe the feature request
Add a new adaptation interface for a method that returns an invocable ID given a sequence(SEQ JSON) and a filename. This gives projects full control over determining invocable IDs for sequences and gives them the ability to handle edge cases/exceptions if needed via special metadata tags or otherwise.
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
Right now, this feature #1539 relies on sequence names to determine how those sequences will be invoked via onboard command. In reality, the ID with which a sequence can be invoked will vary across FSWs. We need a multi-FSW way to determine what the correct invocable id is for any given sequence. Examples: for FCPL seqs, the invocable ID is the onboard name, but for VML, the invocable Id is the seqid.
Describe the feature request
Add a new adaptation interface for a method that returns an invocable ID given a sequence(SEQ JSON) and a filename. This gives projects full control over determining invocable IDs for sequences and gives them the ability to handle edge cases/exceptions if needed via special metadata tags or otherwise.
The text was updated successfully, but these errors were encountered: