39ce35e154
- Gave all possible dom errors distinct names, and throw them on the node side. - Separated errors into FatalDOMError and RetargetableDOMError. Fatal errors are unrecoverable. Retargetable errors could be resolved by requerying the selector. - This exposed a number of unhandled 'notconnected' cases. - Added helper functions to handle errors and ensure TypeScript catches unhandled ones.
28 lines
905 B
TypeScript
28 lines
905 B
TypeScript
/**
|
|
* Copyright (c) Microsoft Corporation.
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
|
|
export type FatalDOMError =
|
|
'error:notelement' |
|
|
'error:nothtmlelement' |
|
|
'error:notfillableelement' |
|
|
'error:notfillableinputtype' |
|
|
'error:notfillablenumberinput' |
|
|
'error:notvaliddate' |
|
|
'error:notinput' |
|
|
'error:notselect';
|
|
|
|
export type RetargetableDOMError = 'error:notconnected';
|