fixing issue 314 #454
Closed
fixing issue 314 #454
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Issue #314 is a little vague. I should have done a better write-up. I think it was resolved by 5488084, and I just failed to close it. I need to figure out if that's correct. In any event, I don't think the issue is referring to the interface map object (interface maps always require a device profile, I think?), but rather support for external systems (those with unknown/unmanaged hardware) in FreeForm. |
|
Closing because I don't think this is a problem since 5488084. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating a pull request fixing 314, and in that added omitempty for DeviceProfileId.